#$KRDBLIB Error System Help
This help provides information on the errors that may happen while  you are running a Visual Basic program.  It provides an indication of the possible cause of the error and what possible actions you may be able to perform to correct the error.

 Help is provided on the following types of errors:
UnrecoverableErrors
RecoverableErrors
Error 6 - Overflow
Out of Memory Errors
Error 11 - Division By Zero
Error in Loading DLL or Custom Control
Error 53 - File Not Found
Error 57 - Device I/O Error
Error 58 - File Already Exists
Error 61 - Disk Full
Error 64 - Bad File Name
Error 67 - Too Many Files
Error 68 - Device Unavailable
Permission Denied
Error 71 - Disk Not Ready
Path/File Access Error
Error 76 - Path Not Found
DDE Errors
Error 282 - No Application Responded To a DDE Initiate
Error 283 - Multiple Applications Responded to DDE Initiate
Error 320 - Can't Use Character Device Name
OLE Errors
Error 31023 - Invalid or Unknown Class
Printer Errors
Help Errors 
ODBC Errors
Data Access Errors
Reserved Errors
DataBase Lock Errors
Error 3022 - Can't Have Duplicate Key
Invalid Account Name or Password Errors
Error 3049 - Database is Corrupted
Error 3050 - SHARE.EXE errors
Can't Open File Errors
Error 3058 - Can't Have Null Value In Index
Database Permission Errors
Null Errors 
Error 3170 - Couldn't Find Installable ISAM

#$+KUnrecoverable Program Errors
{bml BLUEDOT.BMP}Cause
This class of errors is created by a programming error that leads to an error condition that typically can not be recovered from.  The cause may be indicated by the error message.
{bml REDDOT.BMP}Action
Report this problem to the developer by creating and printing a problem report.  Please provide as much information as possible about what you were doing that lead up to the error condition.

You will probably have to Abort the program.  Occasionally you may be able to skip the error and continue.  However, the program is not likely to function correctly after doing so.

#$+KRecoverable Program Errors
{bml BLUEDOT.BMP}Cause
This class of errors is created by a programming error that leads to an error condition that typically can be recovered from.   The cause of the error may be indicated in the error message.
{bml GREENDOT.BMP}Action
Report this problem to the developer by creating and printing a problem report.  Please provide as much information as possible about what you were doing that lead up to the error condition.

You will probably be able to skip the error and continue with minimal, if any, affect on the operation of the program.  However in some cases, the program may not function correctly after continuing or may lead to incorrect or unexpected results.

#$+KError 6 - Overflow
{bml BLUEDOT.BMP}Cause
This error is created by a value becoming greater than expected and exceeding the maximum established for this type of field. 

{bml GREENDOT.BMP}Action
Report this problem to the developer by creating and printing a problem report.  Try to identify the field value(s) that may be exceeding the maximum.

You can try to skip this error.  Either the maximum value or zero will probably be substituted for the invalid value.  This may cause the program to not function as expected or provide incorrect results.

#$+KOut Of Memory Errors
{bml BLUEDOT.BMP}Cause
There is not enough memory remaining to perform the requested function.
{bml GREENDOT.BMP}Action
Reduce the amount of memory currently in use by ending some other applications and then press the Retry button to retry the function.  The easiest way to reduce the memory use of other programs is to terminate them.

If ending other applications does not correct the problem press the Abort button.  Then restart the system and retry the function that originally created the problem.

If all attempts to eliminate the problem are unsuccessful then report the problem to the developer by creating and printing a problem report form and sending it to the developer.  Please provide as much information as possible about the function you were doing that causes the problem.

#$+KError 11 - Division By Zero
{bml BLUEDOT.BMP}Cause
This error is created by a condition that lead to a division by zero.  This may be caused by not entering required data in some cases.   

{bml GREENDOT.BMP}Action
This problem should be reported to the developer so they may add code to the program to prevent the division by zero error from happening.  You can do this by pressing the Create a Problem Error Report button and printing the problem report.
   
You may try skipping this error.  Zero or the maximum value allowed will probably be substituted for the result.  This may cause unexpected results from the program.

#$+KError in Loading DLL or Custom Control
{bml BLUEDOT.BMP}Cause
 An error has occurred in loading a Dynamic Link Library module or custom control for this program.  This may be caused by a failure in the installation process.

{bml REDDOT.BMP}Action
If the installation process was not successful press the Abort button to end this application and then re-install the system.

If this error reoccurs press create a problem report and print the problem report for the developer.

#$+KError 53 - File Not Found
{bml BLUEDOT.BMP}Cause
The file indicated was not found.  This is probably caused by entering an invalid file name.  It may also be caused if some of the system files were not installed correctly.  Occasionally the error may be caused because you did not start the program from the correct working directory.

{bml GREENDOT.BMP}Action
If the problem is a result of you specifying an invalid file name restart the application and specify a correct name.

If the installation process had problems re-install the system.

If you are not running the program from the correct working directory change the Program Manager item to specify the correct working directory.

If the problem keep reoccurring then create a probelm report and print it for the developer.

#$+KDevice I/O Error
{bml BLUEDOT.BMP}Cause
This error is created by an Input/Output error on a device, e.g. floppy disk drive, etc.
 
{bml GREENDOT.BMP}Action
Check the device and the media to insure they are setup properly.  This may be caused by bad media, e.g. floppy disk, etc.  Try a different disk, etc. if possible.
   
After attempting to correct the problem press the Retry button.   

#$+KError 58 - File Already Exists
{bml BLUEDOT.BMP}Cause
The specified file already exists.
{bml GREENDOT.BMP}Action
Specify a different file name if possible.
   
If you want to use this file name either rename or delete the current file with this name.   

#$+KDisk Full
{bml BLUEDOT.BMP}Cause
The disk you were writing to is full. 
{bml GREENDOT.BMP}Action
If possible delete some of the files on the disk to make additional room (You can swap to the file manager to do this).  Then press the Retry button to attempt to continue the function.

If you are writing to a floppy disk you may be able to use a different disk and retry the function.   

#$+KBad File Name
{bml BLUEDOT.BMP}Cause
The file name specified is an invalid file name.  This may be caused by you entering a file name that doesn't follow the DOS file naming conventions.  Valid DOS file names are up to eight characters/digits followed by a period (.) and up to 3 characters/digits.  Only a few special characters are allowed in file names.

{bml GREENDOT.BMP}Action
If possible specify a different file name that follows the file naming conventions.  It may be necessary to abort this run and perform the function again.   

#$+KToo Many Files
{bml BLUEDOT.BMP}Cause
This error is created by the system opening more files than have been allowed for by the operating system.     

{bml GREENDOT.BMP}Action
First attempt to close files in other systems or close other applications and then press the Retry button.

The maximum number of files can be increased by increasing the FILES= parameter in your CONFIG.SYS file.  Consult your DOS documentation or local support staff for additional information.

#$+KError 68 - Device Unavailable 
{bml BLUEDOT.BMP}Cause
A device that the system is attempting to use is not available.  This may be caused by specifying an incorrect device address, e.g.  floppy disk or hard disk drive that does exist.

{bml GREENDOT.BMP}Action
Insure all devices that the system would be using are properly connected and turned on.

If you specified an incorrect drive, correct the drive letter.

You can press the Retry button to attempt the operation again.   

#$+KPermission Denied
{bml BLUEDOT.BMP}Cause
This error was probably caused because you do not have the permission (authority) level required to perform the attempted operation on a file the system is using.

Persmission (authority) levels are usually administered by your Local Area Network (LAN) administrator or security administrator.

{bml REDDOT.BMP}Action
Contact your LAN or security administrator to have them provide the necessary level of permission (authority) to the files used by the system.

#$+KError 71 - Disk Not Ready
{bml BLUEDOT.BMP}Cause
The disk the system is attempting to use is not ready. 
{bml GREENDOT.BMP}Action
Insure the floppy disk is inserted in the diskette drive correctly and fully.
   
Press the Retry button to attempt the operation again.

#$+KError 74 - Path/File Access Error
{bml BLUEDOT.BMP}Cause
This error is probably caused by specifying an incorrect or non-existant path and/or file name.

{bml GREENDOT.BMP}Action
Change the path/file name if possible to a correct file name and/or existing path.
   
It may be necessary to abort the system and then perform the function again with a correct path/file name.   

#$+KError 76 - Path Not Found
{bml BLUEDOT.BMP}Cause
This error is probably caused by specifying an incorrect or non-existant path name.

{bml GREENDOT.BMP}Action
Change the path name if possible to a correct and/or existing path.

It may be necessary to abort the system and then perform the function again with a correct path/file name.   

#$+KDDE Errors
{bml BLUEDOT.BMP}Cause
This error is created by a failure in the DDE communications with another application.

{bml GREENDOT.BMP}Action
Attempt to correct the error condition if it's cause is apparent from the error message.

Attempt to retry the function a few times.  If this does not resolve the problem create a problem report and abort the application.   

#$+KError 282 - No Application Responded To a DDE Initiate
{bml BLUEDOT.BMP}Cause
Another application failed to respond to this application's request to start a DDE conversation.  This may be because the required application is not present on your system.  Or it may be caused by problems in starting the required application.

{bml REDDOT.BMP}Action
Insure the required application is installed on your system.  You may try starting the application yourself and then Retry this function.   

#$+KError 283 - Multiple Applications Responded to DDE Initiate
{bml BLUEDOT.BMP}Cause
There are multiple copies of the requested DDE application running at this time.

{bml GREENDOT.BMP}Action
Switch to and end the last occurrence(s) of the requested DDE application.  A single (the first) occurence of the application should remain running.  Then press the Retry button to attempt the function again.

#$+KError 320 - Can't Use Character Device Name
{bml BLUEDOT.BMP}Cause
 A character device, e.g. PRN, LPT1, etc. may not be used at this point.     

{bml GREENDOT.BMP}Action
Specify a valid file name that does not reference a character device, e.g. PRN, LPT1, etc.   

#$+KOLE Errors
{bml BLUEDOT.BMP}Cause
This class of errors is created by an error condition in an Object Linking & Embedding (OLE) Function.  The specific type of error is indicated in the message.

{bml GREENDOT.BMP}Action
Try to correct the problem if it's cause can be determined from the error message.

Retry the function multiple times.  If the problem persists create and print a problem report for the developer and then abort the program.

#$+KError 31023 - Invalid or Unknown Class
{bml BLUEDOT.BMP}Cause
The object class specified in either invalid or unknown.  This may be because the referenced application is not installed on your system.

{bml REDDOT.BMP}Action
Specify a different object class if possible.
   
Verify that the referenced application is correctly installed on your system.

#$+KPrinter Errors
{bml BLUEDOT.BMP}Cause
Some type of error has occurred on the printer or a function referencing a printer.  The type of error should be indicated in the error message.

{bml GREENDOT.BMP}Action
Attempt to resolve the problem indicated in the error message and then press the Retry button to perform the function again.   

#$+KHelp Errors
{bml BLUEDOT.BMP}Cause
An error occurred in obtaining help.  The specific type of error is indicated in the message provided. 

{bml GREENDOT.BMP}Action
Attempt to correct the problem if it's cause is apparent from the message provided and then retry the function.

If the problem continues, create and print a problem report form for the developer.

#$+KODBC Errors  
{bml BLUEDOT.BMP}Cause
An error occurred while performing an Open Data Base Connectivity (ODBC) related function.  The specific type of error is indicated in the error message.

{bml GREENDOT.BMP}Action
Attempt to correct the cause of the problem if it is apparent from the message provided.  You may need the assistance of your local application and/or database support group to resolve the problem

You may want to create a problem report to assist the developer and/or your local support staff in resolving the problem.

#$+KData Access Errors
{bml BLUEDOT.BMP}Cause
An error has occurred in accessing a database or a database related function.  The specific error is indicated in the error message.

{bml REDDOT.BMP}Action
Attempt to correct the cause of the problem if it is apparent from the error message.  You can retry the function by pressing the Retry button.

If the problem persists create and print a problem report form.   You will problably need the assistance of your local application or database support group or the developer to resolve these problems.   

#$+KDataBase Lock Errors
{bml BLUEDOT.BMP}Cause
The function being attempted requires that the database be "locked", e.g. made available for your exclusive use.  Currently another user or function has the database open so it can't be locked for your exclusive use.

This problem may be caused by high activity rates on your network at times.

{bml GREENDOT.BMP}Action
Attempt to retry the function a few times to see if the problem was a temporary one caused by high activity.
   
If possible have other users terminate the application(s) that are using the database.  Terminate any applications or functions within this application that are using the database.  Then Retry the function.
   
 Some functions, e.g. database reorganizations, repairs, etc. require that a single user be accessing the database.  If you are attempting this type of function try to schedule these activities at a time when other users are not likely to need the database.

#$+KError 3022 - Can't Have Duplicate Key
{bml BLUEDOT.BMP}Cause
An attempt was made to add a row (record) to a database with a key that duplicates an existing record.  

{bml GREENDOT.BMP}Action
Change the key to a different value that does not duplicate an existing key.
   
You may want to use the "Edit" function to edit an existing record instead of adding a new one.

#$+KInvalid Account Name or Password Errors
{bml BLUEDOT.BMP}Cause
The account name and/or password provided is not valid to obtain access to the database. 

{bml GREENDOT.BMP}Action
Provide the correct account name (user id) and password that is required to obtain access to the database.   

#$+KError 3049 - Database is Corrupted
{bml BLUEDOT.BMP}Cause
The database indicated has probably become corrupted.  This can happen if a application that is writing to this database aborts in the middle of an operation.
   
 It is also possible that the file you are referencing is not a Visual  Basic Database at all. 

{bml REDDOT.BMP}Action
If you are referencing an invalid file, correct the file name.
   
Use the "Repair" or "Compress/Reorganize" function within the application or Microsoft Access to attempt repair of the database that is in error.   

#$+KError 3050 - SHARE.EXE errors
{bml BLUEDOT.BMP}Cause
In order to provide multiuser access to database the program SHARE.EXE (or an equivalent program) must be loaded in the system.

{bml REDDOT.BMP}Action
The program SHARE.EXE should exist in your DOS directory.  SHARE can be started by entering the following command 
SHARE /L:500 at the DOS prompt or you can add it to your AUTOEXEC.BAT file.  Consult your application support staff if
you need assistance with this function.

#$+KCan't Open File Errors
{bml BLUEDOT.BMP}Cause
The file indicated couldn't be opened for use.  This generally is caused because another user on the network, or another function on this workstation, has control of the file.

{bml GREENDOT.BMP}Action
If possible have other users terminate the application(s) that are using the database or file.  Terminate any applications or functions within this application that are using the database or file.  Then Retry the function.

Some functions, e.g. database reorganizations, repairs, etc. require that a single user be accessing the database.  If you are attempting this type of function try to schedule these activities at a time when other users are not likely to need the database.

If you are unable to free the database you will need to abort this function.

#$+KError 3058 - Can't Have Null Value In Index
{bml BLUEDOT.BMP}Cause
An attempt was made to add a record with a Null (empty) value in a key field. 

{bml GREENDOT.BMP}Action
Enter a value into all key fields in the record.   

#$+KDatabase Permission Errors
{bml BLUEDOT.BMP}Cause
This error was probably caused because you do not have the permission (authority) level required to perform the attempted operation on the database the system is using.

Persmission (authority) levels are usually administered by your Local Area Network (LAN) administrator or security administrator.

{bml REDDOT.BMP}Action
Contact your LAN or security administrator to have them provide the necessary level of permission (authority) to the databases used by the system.

#$+KNull Errors
{bml BLUEDOT.BMP}Cause
 A null (empty) value is not valid in this context. 
{bml GREENDOT.BMP}Action
If you are entering values for fields enter a value in all required fields.

This error can usually be skipped to allow the program to continue.  If the error persists create and print a problem report form for the developer so they can add code to prevent this error from happening.   

#$+KError 3170 - Couldn't Find Installable ISAM
{bml BLUEDOT.BMP}Cause
The system could not find the database drivers required to access a database.  Normally these drivers are located in the windows system directory.  The location of these drivers must be defined in the INI file for the application. 

{bml REDDOT.BMP}Action
Insure that the application has an INI file in your windows directory.   Also insure that it has entries for the installable ISAM drivers you will be using.  Contact the developer and/or your local application support staff for assistance in setting up a proper INI file for the application.        

#$+KError 3000 - Reserved Error
{bml BLUEDOT.BMP}Cause
An unexpected (reserved) error has occurred.  The specific error code is normally indicated in the error message.  Frequently these errors are caused by new errors from the database manager.
{bml GREENDOT.BMP}Action
If the error code indicated in the message is in one of the groups listed below click on it to get additional information.

If the error code is not one of the ones below, the message may provide additional information.  If you can fix the problem causing the error, do so and click the Retry button.  If you can not fix the error, click the Abort button.

Errors -1010 through -1068
Error -1209
Errors -1210 through -1911
Errors -2030 through -2034
Errors -3028 through -3077
Errors -3520 through -3561
Errors -3601 through -3708
Error -5017 Numeric field overflow.
Errors -5015 through -5214
Error -8181 Record in table '_' was deleted by another user.
Error -8182 Record in table '_' is locked by another user.
Error -8194 
Errors -8056 through  -8197
Errors -8220 through -8274
Errors -20000 through  -32020

#$+KReserved Errors -1010 Through -1068
  -1010 Invalid database ID.
  -1016 Can't have more than 10 fields in an index.
  -1029 Database engine hasn't been initialized.
  -1030 Database engine has already been initialized.
  -1034 Query support unavailable.
  -1046 Can't delete a field that is part of an index.
  -1051 Can't delete this index.  It is either the current index or is used in a relationship.
  -1062 Can't create database; Invalid locale.
  -1066 Can't create a relationship.
  -1068 Invalid referential integrity constraint.

{bml BLUEDOT.BMP}Cause
These errors are caused by errors within the program you are running.  The error message indicates the specific error condition.

{bml REDDOT.BMP}Action
Create and print a problem report form for the developer.  Provide as much information as possible to assist the developer determine the cause of the problem.

You can try ignoring the error, but you will probably have to Abort the program.

#$+KReserved Errors -1209 Through -1911
  -1308 Can't define field or index in a table that contains data.
  -1309 Can't modify table structure.  Another user has the table open.
  -1315 Can't change a rule while the rules for this table are in use.
  -1316 Object is invalid for operation.
  -1402 Primary key already exists.
  -1403 Index already exists.
  -1406 Invalid index definition.
  -1513 Can't create index on Memo field or OLE Object field.
  -1519 Can't delete this field.  It's part of one or more relationships.
  -1523 Zero-length string is valid only in a text or Memo field.
  -1601 The key was not found. (JET_errRecordNotFound)
  -1802 Can't open |9 system database (typically SYSTEM.MDA).
  -1910 You must enter a personal identifier (PID) consisting of at least four and no more than 20 characters and digits.
  -1911 Account name already exists.

{bml BLUEDOT.BMP}Cause
All of these errors are caused by errors within the program you are running.  The error message indicates the specific error condition.

{bml REDDOT.BMP}Action
Create and print a problem report form for the developer.  Provide as much information as possible to assist the developer determine the cause of the problem.

You can try ignoring the error, but you will probably have to Abort the program.

#$+KErrors -2030 through -2034
  -2030 There are several tables with that name. Please specify owner in the format 'owner.table'.
  -2031 Invalid connection string in pass-through query.
  -2032 Single-row update/delete affected more than one row of a remote table.  Index specified as unique contains duplicate values.
  -2033 The server's MSysConf table exists, but is in an incorrect format.  Contact your system administrator.
  -2034 You cannot use ODBC to attach an external Microsoft Access or ISAM database table to your database.

{bml BLUEDOT.BMP}Cause
All of these errors are caused by errors within the program you are running.  The error message indicates the specific error condition.

{bml REDDOT.BMP}Action
Create and print a problem report form for the developer.  Provide as much information as possible to assist the developer determine the cause of the problem.

You can try ignoring the error, but you will probably have to Abort the program.

#$+KErrors -3028 through -3077
  -3028 Can't have action query as an input.
  -3031 Query does not return records.
  -3059 This query is not a properly formed data-definition query.
  -3060 No database specified in connection string or IN clause.
  -3063 At most one field can be returned from a subquery that doesn't use the EXISTS keyword.
  -3064 The number of columns in the two selected tables or queries of a union query don't match.
  -3066 Execute method must be used on action or data-definition queries.
  -3069 Pass-through query with ReturnsRecords property set to True did not return any records.
  -3070 At most one record can be returned by this subquery."
  -3071 Query is too complex.
  -3072 Unions not allowed in a subquery.
  -3073 Can't perform join, group, or sort. Combined fields are too long.
  -3077 Too many FastFind Sessions were invoked.

{bml BLUEDOT.BMP}Cause
All of these errors are caused by errors within the program you are running.  The error message indicates the specific error condition.

{bml REDDOT.BMP}Action
Create and print a problem report form for the developer.  Provide as much information as possible to assist the developer determine the cause of the problem.

You can try ignoring the error, but you will probably have to Abort the program.

#$+KErrors -3520 through -3561
  -3520 Number  of query values and destination fields aren't the same.
  -3530 Join expression not supported.
  -3531 Can be present only in version 1.0 format.
  -3532 Syntax error in union query.
  -3535 Pass-through query must contain at least one character.
  -3550 Syntax error in CONSTRAINT clause.
  -3551 Syntax error in CREATE TABLE statement.
  -3552 Syntax error in CREATE INDEX statement.
  -3553 Syntax error in field definition.
  -3554 Syntax error in ALTER TABLE statement.
  -3555 Syntax error in DROP INDEX statement.
  -3556 Syntax error in DROP TABLE statement.
  -3560 Relationship must be on the same number of fields with the same data types.
  -3561 Can't find field in index definition.

{bml BLUEDOT.BMP}Cause
All of these errors are caused by errors within the program you are running.  The error message indicates the specific error condition.

{bml REDDOT.BMP}Action
Create and print a problem report form for the developer.  Provide as much information as possible to assist the developer determine the cause of the problem.

You can try ignoring the error, but you will probably have to Abort the program.

#$+KErrors -3601 through -3708
  -3601Property setting can't be larger than 2 KB.
  -3602 This property isn't supported for external data sources or for databases created in a previous version of |9.
  -3603 Property specified already exists.
  -3604 DeleteOnly called with non-zero cbData.
  -3605 An error has occurred.  Properties were not saved.
  -3606 Can't save property; property is a schema property.
  -3700 Validation rules and default values can't be placed on system or attached tables.
  -3704 Can't place this validation expression on this field.
  -3708 Syntax error in default value.

{bml BLUEDOT.BMP}Cause
These errors are caused by errors within the program you are running.  The error message indicates the specific error condition.

{bml REDDOT.BMP}Action
Create and print a problem report form for the developer.  Provide as much information as possible to assist the developer determine the cause of the problem.

You can try ignoring the error, but you will probably have to Abort the program.

#$+KErrors -5015 through -5214
  -5015 External table isn't in the expected format.
  -5016 Unexpected error from external database driver (|).
  -5020 Paradox index is not primary.
  -5029 Can't open '|'.  Another user has the table open using a different network control file or locking style.
  -5030 Can't open this Paradox 4.x table because ParadoxNetStyle is set to 3.x in |8.
  -5112 Format of memo file doesn't match specified external database format.
  -5210 Btrieve: Invalid IndexDDF option in |8.
  -5211 Invalid DataCodePage option in |8.
  -5212 Btrieve: Xtrieve options aren't correct in |8.
  -5213 Btrieve: Can't find file FIELD.DDF.
  -5214 Btrieve: Invalid IndexDeleteRenumber option in |8.

{bml BLUEDOT.BMP}Cause
All of these errors are caused by errors within the program you are running.  The error message indicates the specific error condition.

{bml REDDOT.BMP}Action
Create and print a problem report form for the developer.  Provide as much information as possible to assist the developer determine the cause of the problem.

You can try ignoring the error, but you will probably have to Abort the program.

#$+KErrors -8056 through  -8197
  -8056 No destination field name in INSERT statement (|).
  -8172 Top not allowed in delete queries.
  -8175 Crosstab query contains one or more invalid fixed column headings.
  -8176 Query '|' is corrupt.
  -8177 Invalid TOP argument in select query.
  -8178 This Recordset is not updatable.
  -8179 Field '|' is based on an expression and can't be edited.
  -8180 Table '|2' is read-only.
  -8183 To make changes to this field, first save the record.
  -8184 Can't enter value into blank field on 'one' side of outer join.
  -8185 Records in table '|' would have no record on the 'one' side.
  -8186 Current field must match join key '|' on 'one' side of outer join.
  -8187 Invalid Memo or OLE object in subquery '|'.
  -8188 Unrecognized database format '|'.
  -8189 ORDER BY expression (|) uses non-output fields.
  -8190 Unknown or invalid reference '|1' in validation expression or default value in table '|2'.
  -8191 Unknown or invalid field reference '|'.
  -8192 Can't add record(s); primary key for table '|' not in recordset.
  -8193 Can't add record(s); join key of table '|' not in recordset.
  -8195 Record(s) can't be added; no corresponding record on the 'one' side.
  -8196 Can't use Memo or OLE object field '|' in SELECT clause of a union query.
  -8197 Unknown function '|2' in validation expression or default value on '|1'.

{bml BLUEDOT.BMP}Cause
All of these errors are caused by errors within the program you are running.  The error message indicates the specific error condition.

{bml REDDOT.BMP}Action
Create and print a problem report form for the developer.  Provide as much information as possible to assist the developer determine the cause of the problem.

You can try ignoring the error, but you will probably have to Abort the program.

#$+KErrors -8220 through -8274
  -8220 Can't modify the design of table '|'.  It's in a
        read-only database.
  -8221 Can't find table or constraint.
  -8222 No such index '|2' on table '|1'.
  -8223 Can't create relationship.  Referenced table '|' doesn't
        have a primary key.
  -8224 The specified fields are not uniquely indexed in table
        '|'.
  -8225 Table '|1' already has an index named '|2'
  -8226 Table '|' doesn't exist.
  -8227 No such relationship '|2' on table '|1'.
  -8228 There is already a relationship named '|' in the current
        database.
  -8229 Can't create relationships to enforce referential
        integrity.  Existing data in table '|2' violates
        referential integrity rules with related table '|1'.
  -8230 Field '|2' already exists in table '|1'.
  -8231 There is no field named '|2' in table '|1'.
  -8232 Field '|' size must be 1 to 255.
  -8233 Can't delete field '|'.  It's part of one or more
        relationships.
  -8234 There is no primary key in table '|'.
  -8235 Invalid field name '|' in definition of index or
        relationship.
  -8260 | in table-level validation expression.
  -8261 Field '|' can't contain a null value.
  -8262 Field '|' can't be a zero-length string.
  -8263 This validation rule must be met.
  -8264 Can't perform cascading operation.  Since related records
        exist in table '|', referential integrity rules would be
        violated.
  -8265 Can't perform cascading operation.  There must be a
        related record in table '|'.
  -8266 Can't perform cascading operation.  It would result in a
        null key in table '|'.
  -8267 Can't perform cascading operation.  It would result in a
        duplicate key in table '|'.
  -8268 Can't perform cascading operation.  It would result
        in two updates on field '|2' in table '|1'.
  -8269 Can't perform cascading operation.  It would cause field
        '|' to become null, which is not allowed.
  -8270 Can't perform cascading operation.  It would cause field
        '|' to become a zero-length string, which is not allowed.
  -8271 Can't perform cascading operation:  '|'
  -8272 Invalid entry.  Can't perform cascading operation
        specified in table '|1' because value entered is too big
        for field '|2'.
  -8273 |
  -8274 Can't perform cascading update on table '|' because it is
        currently in use.

#$+KErrors -20000 through  -32020
  -20000 Can't open this database for update.
  -30001 No fields defined - cannot append table.
  -30002 Name not found in this collection.
  -30003 Can't append.  Field is part of a TableDefs collection.
  -30004 Property can be set only when the field is part of a Recordset object's Fields collection.
  -30005 Can't set this property once the object is part of a collection.
  -30006 Can't append.  Index is part of a TableDefs collection.
  -30007 Property not found.
  -30008 Invalid property value.
  -30009 Object isn't a collection.
  -30010 Method not applicable for this object.
  -30011 Can't set this property for remote objects.
  -30012 Can't append a relation with no fields defined.
  -30013 Can't append.  Object already in collection.
  -30014 Can't delete a built-in property.
  -30015 Property '|' must be set before using this method.
  -30016 User-defined properties don't support a Null value.
  -30017 Object is no longer valid.
  -30018 This method or property is not currently available on this Recordset.
  -30019 The action was canceled by an associated object.
  -30020 Error in DAO automation.
  -30021 Data type conversion error.
  -32020 Can't import table or query.  No records found, or all records contain errors.

{bml BLUEDOT.BMP}Cause
All of these errors are caused by errors within the program you are running.  The error message indicates the specific error condition.

{bml REDDOT.BMP}Action
Create and print a problem report form for the developer.  Provide as much information as possible to assist the developer determine the cause of the problem.

You can try ignoring the error, but you will probably have to Abort the program.

#$+K-8181 Record in table '_' was deleted by another user.
{bml BLUEDOT.BMP}Cause
The record you were updating has been deleted by another user.

{bml GREENDOT.BMP}Action
You must add the record using the add function.  You will probably want to determine who has deleted the record and verify if the record should be deleted.

#$+KError -8182 Record in table '_' is locked by another user.
{bml BLUEDOT.BMP}Cause
The record you are trying to update is currently locked by another user.

{bml GREENDOT.BMP}Action
Retry the function a few times, with a delay in between so the other user can complete their update.  If the error does not go away after a number of tries you will have to abort the program and redo the update you were attempting.

#$+KError -1209
The Jet database engine has encountered a problem in your  database.  To correct the problem, you must repair and compact the database.
{bml BLUEDOT.BMP}Cause
The database indicated has probably become corrupted.  This can happen if a application that is writing to this database aborts in the middle of an operation.
   
 It is also possible that the file you are referencing is not a Visual  Basic Database at all. 

{bml REDDOT.BMP}Action
If you are referencing an invalid file, correct the file name.
   
Use the "Repair" or "Compress/Reorganize" function within the application or Microsoft Access to attempt repair of the database that is in error.   

#$+KError -8194
The database is opened by user '|2' on machine '|1'.  You can't open this database exclusively.
{bml BLUEDOT.BMP}Cause
The function being attempted requires that the database be "locked", e.g. made available for your exclusive use.  Currently another user or function has the database open so it can't be locked for your exclusive use.

This problem may be caused by high activity rates on your network at times.

{bml REDDOT.BMP}Action
Attempt to retry the function a few times to see if the problem was a temporary one caused by high activity.
   
If possible have other users terminate the application(s) that are using the database.  Terminate any applications or functions within this application that are using the database.  Then Retry the function.
   
 Some functions, e.g. database reorganizations, repairs, etc. require that a single user be accessing the database.  If you are attempting this type of function try to schedule these activities at a time when other users are not likely to need the database.

#$KData Access Errors
{bml BLUEDOT.BMP}Cause
An error has occurred in accessing a database or a database related function.  The specific error is indicated in the error message.

{bml REDDOT.BMP}Action
Attempt to correct the cause of the problem if it is apparent from the error message.  You can retry the function by pressing the Retry button.

If the problem persists create and print a problem report form.   You will problably need the assistance of your local application or database support group or the developer to resolve these problems.   

#$KData Access Errors
{bml BLUEDOT.BMP}Cause
An error has occurred in accessing a database or a database related function.  The specific error is indicated in the error message.

{bml REDDOT.BMP}Action
Attempt to correct the cause of the problem if it is apparent from the error message.  You can retry the function by pressing the Retry button.

If the problem persists create and print a problem report form.   You will problably need the assistance of your local application or database support group or the developer to resolve these problems.